Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update plugin parent POM and plugin BOM #241

Merged
merged 1 commit into from
Apr 24, 2022
Merged

Conversation

basil
Copy link
Member

@basil basil commented Apr 23, 2022

No description provided.

@basil basil force-pushed the pom branch 2 times, most recently from 9b7654e to 3414f37 Compare April 24, 2022 02:21
@tszmytka tszmytka added the dependencies (release-drafter) label Apr 24, 2022
@tszmytka tszmytka merged commit 5de02ed into jenkinsci:master Apr 24, 2022
@basil basil deleted the pom branch April 24, 2022 13:43
@basil
Copy link
Member Author

basil commented Apr 24, 2022

Thank you, @tszmytka! A release of this would facilitate Java 17 PCT testing.

@basil
Copy link
Member Author

basil commented May 11, 2022

Gentle ping; a release of this would help me move forward with some draft PRs in jenkinsci/bom.

@dblock dblock mentioned this pull request May 11, 2022
@dblock
Copy link
Member

dblock commented May 11, 2022

I opened #243

@basil
Copy link
Member Author

basil commented May 11, 2022

Thanks @dblock! BTW if you implement automated plugin release then releasing a plugin becomes as simple as adding a special label when merging PRs.

@dblock
Copy link
Member

dblock commented May 12, 2022

@basil Care to contribute? Let us know what you need from @tszmytka or I?

@basil
Copy link
Member Author

basil commented May 12, 2022

If you are suggesting that I contribute more to Jenkins, you must not have seen my GitHub profile. I have made my contribution to this plugin. What I need from the plugin maintainers is for that contribution to be released so that I can do plugin compatibility testing with it.

@dblock
Copy link
Member

dblock commented May 12, 2022

@basil Thanks for your contributions. I am just saying that by the looks of that doc there's a bunch of things to change in this project. If you want to do it, it will get done faster.

@basil
Copy link
Member Author

basil commented May 12, 2022

But if I propose a PR to implement automated plugin release, I risk that my time would be wasted because the maintainers do not want to use automated plugin release. The decision about whether or not to use automated plugin release belongs to the maintainers, not to me. Therefore, it makes sense for the same maintainers to implement automated plugin release. If the maintainer chooses not to implement automated plugin release, it is the maintainer's responsibility to do manual releases.

@dblock
Copy link
Member

dblock commented May 14, 2022

I am a maintainer and can confirm that we want tag-based automated plugin release.

@basil
Copy link
Member Author

basil commented May 14, 2022

I am a maintainer and can confirm that we want tag-based automated plugin release.

Then I suggest you follow the instructions in Setting up automated plugin release , or (if you decline to follow those instructions) to perform a manual release. I will not do this work for you. It is the responsibility of the plugin maintainer, not contributors, to handle releases.

@dblock
Copy link
Member

dblock commented May 14, 2022

@basil Thank you for your helpful suggestions. I will release this plugin sometime next month.

@basil
Copy link
Member Author

basil commented Jul 23, 2022

I will release this plugin sometime next month.

But two months later?

@dblock
Copy link
Member

dblock commented Jul 24, 2022

Well, I tried. Could use some help, #247 (comment)

@basil
Copy link
Member Author

basil commented Jul 24, 2022

Well, I tried. Could use some help, #247 (comment)

On July 24, I provided the help that was requested: #247 (comment)

@dblock
Copy link
Member

dblock commented Jul 25, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies (release-drafter)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants